Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use IMU measurements to set submodel base state in RDE #793

Merged
merged 18 commits into from
Jan 26, 2024

Conversation

isorrentino
Copy link
Collaborator

@isorrentino isorrentino commented Jan 8, 2024

This PR implements what is described in #70 and #95.
In addition, the PR introduces a code restructure to have the possibility to define more than one measurement dynamics for a given sensor.
The tests have been modified accordingly.

[UPDATE] I added also the possibility of having the friction torques as a measurement for the estimator.

@@ -0,0 +1,522 @@
# Changelog
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you remove this file?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

CHANGELOG.md Outdated
@@ -15,6 +15,7 @@ All notable changes to this project are documented in this file.
- Add the support of QP problems with no constraint in `QPInverseKinematics` and `QPTSID` (https://github.com/ami-iit/bipedal-locomotion-framework/pull/784)
- Implement `blf-joints-grid-position-tracking` application in `utilities` (https://github.com/ami-iit/bipedal-locomotion-framework/pull/787)
- Add the possibility to resample the contact in a given contact list (https://github.com/ami-iit/bipedal-locomotion-framework/pull/788)
- Set submodel states from IMUs in RDE (Use IMU measurements to set submodel base state in RDE)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you rebase the PR on top of master and move this line to unreleased?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@isorrentino
Copy link
Collaborator Author

@GiulioRomualdi after the rebase the CI fails.

@isorrentino
Copy link
Collaborator Author

@traversaro I requested also your review to be sure about the implemented formulas. If you can check the code here

for (int subModelIdx = 0; subModelIdx < m_subModelList.size(); subModelIdx++)
that is where I take the imu measurements to set the submodel base states and compute the forward dynamics as discussed in https://github.com/ami-iit/element_sensorless-torque-control/issues/70, it would be great :)

@traversaro
Copy link
Collaborator

@traversaro I requested also your review to be sure about the implemented formulas. If you can check the code here

for (int subModelIdx = 0; subModelIdx < m_subModelList.size(); subModelIdx++)

that is where I take the imu measurements to set the submodel base states and compute the forward dynamics as discussed in ami-iit/element_sensorless-torque-control#70, it would be great :)

Th computation seems correct. However, formula in

m_baseAcceleration.coeffs().head(3).noalias()
are not obvious, so if you could add a reference (for example with a comment) for that equation it would be great.

@GiulioRomualdi
Copy link
Member

Hi @isorrentino can you rebase the PR on top of master?

@isorrentino
Copy link
Collaborator Author

Hi @isorrentino can you rebase the PR on top of master?

Done.

@GiulioRomualdi GiulioRomualdi enabled auto-merge (squash) January 26, 2024 16:02
@GiulioRomualdi GiulioRomualdi merged commit a9f2166 into ami-iit:master Jan 26, 2024
12 checks passed
@isorrentino isorrentino deleted the rde/IMU-as-base branch February 9, 2024 14:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants